@Trott Browserify relies on querystring-es3, so any fix here wouldn't fix issue over there.

Also discussion about inconsistency with node is handled now at #6

I will happily merge updates from this repo into https://github.com/mike-spainhower/querystring if they happen to be ES3 compatible. Anything incompatible would be handled separately via issue or PR in the fork.

This issue seems to have long consequences, see mike-spainhower#4

@dfcreative issue you meantion is about querystring-es3 (not this project) being incompatible with node. querystring-es3 is different project maintained by different person.

@medikoo the owner refers to your repository as a source of incompatibility

@dfcreative owner then should rely on Node.js and not this package

@dfcreative incompatibility discussion you linked, is actually a different matter, and it's not related to how querystring natively works in Node.js, it's about incompatibility with one of the goals of Browserify, read carefully linked issue.

...and I think this issue is related with this pull request too.

If we ignore the incompatibilities with Browserify, is there anything that is keeping this from being merged?

FWIW I just updated the es3-compatible version and will be publishing it shortly behind a major bump - https://github.com/SpainTrain/querystring-es3

Feel free to review and flag any issues.

See proposed roadmap: #20 it covers also ES3 version, PR's are very welcome (and I will handle them promptly).

I'm going to close it as it all should be addressed with new published versions